programming4us
           
 
 
Applications Server

Microsoft Dynamic GP 2010 : Bank Reconciliation

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
7/3/2013 9:46:52 PM

The Bank Reconciliation module is also sometimes referred to as Bank Rec or Cash Management and it is part of the Financial series in Dynamics GP. The menu choices for Bank Reconciliation will start with Financial, while the SQL tables will start with CM. Setup for the Bank Reconciliation module consists of two steps—setting up Checkbooks and Bank Reconciliation Setup.

Even if you do not own or are not planning on using the Bank Reconciliation module, you will need to perform the checkbook setup in Dynamics GP. This will be used in many other modules throughout the system.


Checkbooks

A Checkbook in Dynamics GP represents a bank account. In a typical company, each individual bank account will have a unique General Ledger account. The Dynamics GP checkbook setup will allow you to link each bank account to a GL account and keep track of the next available check and deposit numbers for the bank account. Most modules in Dynamics GP use a Checkbook ID (as opposed to the GL account number) to represent a bank account.

You can create an unlimited number of checkbooks in Dynamics GP. To set up or modify a checkbook, navigate to Cards | Financial | Checkbook. Following are explanations for the fields on the Checkbook Maintenance window:

  • Checkbook ID: The Checkbook ID is alphanumeric (up to 15 characters) and will be used throughout Dynamics GP to identify a bank account. It is recommended to make this ID something easy for users to identify. For example, if you have multiple accounts with the same bank, consider what users typically call them. The IDs might represent their names such as CHASE CHECKING and CHASE SAVINGS, or maybe contain part of the account number such as CHASE 1833 and CHASE 5869. Once created, the Checkbook ID cannot be changed without the purchase of an additional tool.

  • Description: The name of the bank account and what will help users identify the correct bank account in a list if the Checkbook ID is not enough. This will allow up to 30 characters. If there are multiple similar accounts, consider putting the account number, or part of it, into the description, especially if it is not part of the Checkbook ID.

  • Inactive: Once a bank account is no longer used, you can make it inactive to prevent users from entering transactions to it. Inactive checkbooks still show up on inquiries, but attempting to enter a transaction for one will result in an error.

  • Currency ID, Payment Rate Type, and Deposit Rate Type: Choose the appropriate currency and rate types for the bank account.

  • Cash Account: The GL account corresponding to this bank account. It is important to have a one-to-one relationship between bank accounts and GL accounts to allow for smooth bank reconciliations.

  • Next Check Number: Enter the next check number you will be using. Dynamics GP will automatically increment check numbers as checks are printed or entered in various modules. Note that you will need to manually increment the number of digits. For example, if you have set up the check number with four digits, once you reach 9999, the system will not automatically go to 10000, it will update to 0000. While you can add more digits at any time, this will not update check numbers that have already been used, so your check numbers will have different lengths and may not sort properly on lookups or reports. Consider entering an extra zero or two in front of the numbers at the onset, so if your next check number is 6001, you could start with 06001 or 006001, depending on the expected volume of checks.

  • Next Deposit Number: Enter the next deposit number you would like to use. Typically deposit slips are not numbered, so this is more of an internal number. Many companies like to use the prefix DEP to clearly identify deposits on a list of bank transactions. As with the check numbers, the deposit numbers will not automatically increment the number of digits, so it is recommended to use a number with enough total digits to last for some time.

  • Company Address ID, Bank Account, and Bank ID: These fields are optional and, unless needed by other modules, most companies typically leave these blank.

  • User-Defined 1 and 2: If there is additional information you would like to track about your bank account, you can use these two fields. The labels for these can be changed on the Bank Reconciliation Setup window (Microsoft Dynamics GP | Tools | Setup | Financial | Bank Reconciliation).

  • Last Reconciled Balance and Date: These are used to populate your last reconciliation information prior to starting to use Dynamics GP Bank Reconciliation. You can leave these blank until you are ready to perform your first bank reconciliation.

  • Payables Options:

    • Max Check Amount and Password: With these you can limit the maximum amount for payables checks and optionally set up a password to override the maximum. Leaving the amount at zero will allow checks of any amount to be created.

    • Duplicate Check Numbers: It is recommended to uncheck (disallow) this option so that duplicate check numbers are not inadvertently entered, thus causing problems during bank reconciliation.

    • Override Check Number: Usually it is helpful to leave this checked (allowed), so that when payables checks are printed, the user can override the next check number if for some reason it is not coming up correctly.

The following is an example of a typical Checkbook Maintenance window:

Bank Reconciliation Setup

Bank Reconciliation setup determines the defaults for the Bank Reconciliation module. If you are not using the Bank Reconciliation module, or not implementing it yet, you can skip this step. To open the Bank Reconciliation Setup window, navigate to Microsoft Dynamics GP | Tools | Setup | Financial | Bank Reconciliation. The following list explains the fields on this window:

  • Next Number: This will be the next number used on a bank transaction or bank transfer. This is an internal number and there is typically no reason to change this from the default; it will increment automatically as needed.

  • Transaction Type, Description, and Code: These are default descriptions and codes assigned to each type of Bank Reconciliation transaction. It is recommended not to change these descriptions and codes, as having them differ from the defaults will make it difficult to consult with others about any questions you might have on the Bank Reconciliation module.

  • Reconcile Adjustment Type, Description, and Code: Similar to the previous option, these are descriptions and codes assigned to Bank Reconciliation adjustments and changing them is not recommended.

  • Maintain History: This is checked by default, it is recommended to leave it selected and keep all history.

  • Defaults:

    • Checkbook ID: Optionally, you can specify a default Checkbook ID for your Bank Reconciliation transactions. This may save time during data entry if most bank transactions use the same bank account. Checkbooks have to be set up first to be able to select them as a default. If there are many checkbooks being used, consider leaving this default blank to force users to pick a checkbook for each transaction. Note that if the Multicurrency module is enabled, most Dynamics GP windows will not use this checkbook ID default.

    • User-Defined 1 and 2: This field allows you to change the labels that appear for the user-defined fields on the Checkbook Maintenance window.

The following screenshot shows the Bank Reconciliation Setup window:

Other -----------------
- Microsoft Dynamic GP 2010 : General Ledger
- Using Non-Windows Systems to Access Exchange Server 2007 : Mac OS X Mail
- Using Non-Windows Systems to Access Exchange Server 2007 : Outlook Express
- Using Non-Windows Systems to Access Exchange Server 2007 : Understanding Non-Windows–Based Mail Client Options
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 8) - Consuming Web Services from Dynamics AX
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 7) - Sending One-Way Requests from Dynamics AX
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 6) - Working with Document Services - Consuming Dynamics AX Services
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 5) - Working with Document Services - Publishing Dynamics AX Services, Configuring Dynamics AX Services
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 4) - Working with Document Services - Customizing Document Services
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 3) - Working with Custom Services
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 2) - Components of Dynamics AX Services
- Microsoft Dynamics AX 2009 : The Application Integration Framework (part 1)
- Microsoft Systems Management Server 2003 : Rolling Back and Uninstalling a Scripted Installation
- Microsoft Systems Management Server 2003 : Modifying Installation Scripts Using Script Editor (part 2) - Modifying the Script, Windows Installer Step-Up Utility Buttons
- Microsoft Systems Management Server 2003 : Modifying Installation Scripts Using Script Editor (part 1) - Script Editor Variables and Actions
- System Center Configuration Manager 2007 : Architecture Design Planning - Site Planning
- System Center Configuration Manager 2007 : Hierarchy Planning
- Microsoft Systems Management Server 2003 : Modifying Installation Scripts Using the Installation Expert (part 2)
- Microsoft Systems Management Server 2003 : Modifying Installation Scripts Using the Installation Expert (part 1)
- Sizing Considerations for mySAP Components (part 2) - Sizing mySAP Business Intelligence & Sizing mySAP SRM
 
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
- First look: Apple Watch

- 3 Tips for Maintaining Your Cell Phone Battery (part 1)

- 3 Tips for Maintaining Your Cell Phone Battery (part 2)
programming4us programming4us